SonarSource Rules
  • Products

    In-IDE

    Code Quality and Security in your IDE with SonarQube Ide

    IDE extension that lets you fix coding issues before they exist!

    Discover SonarQube for IDE

    SaaS

    Code Quality and Security in the cloud with SonarQube Cloud

    Setup is effortless and analysis is automatic for most languages

    Discover SonarQube Cloud

    Self-Hosted

    Code Quality and Security Self-Hosted with SonarQube Server

    Fast, accurate analysis; enterprise scalability

    Discover SonarQube Server
  • SecretsSecrets
  • ABAPABAP
  • AnsibleAnsible
  • ApexApex
  • AzureResourceManagerAzureResourceManager
  • CC
  • C#C#
  • C++C++
  • CloudFormationCloudFormation
  • COBOLCOBOL
  • CSSCSS
  • DartDart
  • DockerDocker
  • FlexFlex
  • GitHub ActionsGitHub Actions
  • GoGo
  • HTMLHTML
  • JavaJava
  • JavaScriptJavaScript
  • JSONJSON
  • JCLJCL
  • KotlinKotlin
  • KubernetesKubernetes
  • Objective CObjective C
  • PHPPHP
  • PL/IPL/I
  • PL/SQLPL/SQL
  • PythonPython
  • RPGRPG
  • RubyRuby
  • RustRust
  • ScalaScala
  • SwiftSwift
  • TerraformTerraform
  • TextText
  • TypeScriptTypeScript
  • T-SQLT-SQL
  • VB.NETVB.NET
  • VB6VB6
  • XMLXML
  • YAMLYAML
C

C static code analysis

Unique rules to find Bugs, Vulnerabilities, Security Hotspots, and Code Smells in your C code

  • All rules 315
  • Vulnerability13
  • Bug76
  • Security Hotspot19
  • Code Smell207

  • Quick Fix 19
 
Tags
    Impact
      Clean code attribute
        1. Hard-coded secrets are security-sensitive

           Security Hotspot
        2. "sprintf" should not be used

           Security Hotspot
        3. Changing working directories without verifying the success is security-sensitive

           Security Hotspot
        4. Setting capabilities is security-sensitive

           Security Hotspot
        5. Using "tmpnam", "tmpnam_s" or "tmpnam_r" is security-sensitive

           Security Hotspot
        6. Using "strncpy" or "wcsncpy" is security-sensitive

           Security Hotspot
        7. Using "strncat" or "wcsncat" is security-sensitive

           Security Hotspot
        8. Using "strcat" or "wcscat" is security-sensitive

           Security Hotspot
        9. Using "strlen" or "wcslen" is security-sensitive

           Security Hotspot
        10. Changing directories improperly when using "chroot" is security-sensitive

           Security Hotspot
        11. Using "strcpy" or "wcscpy" is security-sensitive

           Security Hotspot
        12. Using publicly writable directories is security-sensitive

           Security Hotspot
        13. Using clear-text protocols is security-sensitive

           Security Hotspot
        14. Expanding archive files without controlling resource consumption is security-sensitive

           Security Hotspot
        15. Using weak hashing algorithms is security-sensitive

           Security Hotspot
        16. Setting loose POSIX file permissions is security-sensitive

           Security Hotspot
        17. Using pseudorandom number generators (PRNGs) is security-sensitive

           Security Hotspot
        18. Hard-coded passwords are security-sensitive

           Security Hotspot
        19. Using hardcoded IP addresses is security-sensitive

           Security Hotspot

        Using "strlen" or "wcslen" is security-sensitive

        consistency - conventional
        security
        Security Hotspot
        • cwe
        • cert

        The function size_t strlen(const char *s) measures the length of the string s (excluding the final null character).
        The function size_t wcslen(const wchar_t *s) does the same for wide characters, and should be used with the same guidelines.

        Similarly to many other functions in the standard C libraries, strlen and wcslen assume that their argument is not a null pointer.

        Additionally, they expect the strings to be null-terminated. For example, the 5-letter string "abcde" must be stored in memory as "abcde\0" (i.e. using 6 characters) to be processed correctly. When a string is missing the null character at the end, these functions will iterate past the end of the buffer, which is undefined behavior.

        Therefore, string parameters must end with a proper null character. The absence of this particular character can lead to security vulnerabilities that allow, for example, access to sensitive data or the execution of arbitrary code.

        Ask Yourself Whether

        • There is a possibility that the pointer is null.
        • There is a possibility that the string is not correctly null-terminated.

        There is a risk if you answered yes to any of those questions.

        Recommended Secure Coding Practices

        • Use safer functions. The C11 functions strlen_s and wcslen_s from annex K handle typical programming errors.
          Note, however, that they have a runtime overhead and require more code for error handling and therefore are not suited to every case.
        • Even if your compiler does not exactly support annex K, you probably have access to similar functions.
        • If you are writing C++ code, using std::string to manipulate strings is much simpler and less error-prone.

        Sensitive Code Example

        size_t f(char *src) {
          char dest[256];
          strncpy(dest, src, sizeof dest); // Truncation may happen
          return strlen(dest); // Sensitive: "dest" will not be null-terminated if truncation happened
        }
        

        Compliant Solution

        size_t f(char *src) {
          char dest[256];
          strncpy(dest, src, sizeof dest); // Truncation may happen
          dest[sizeof dest - 1] = 0;
          return strlen(dest); // Compliant: "dest" is guaranteed to be null-terminated
        }
        

        See

        • CWE - CWE-120 - Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
        • CERT, STR07-C. - Use the bounds-checking interfaces for string manipulation
        • STIG Viewer - Application Security and Development: V-222612 - The application must not be vulnerable to overflow attacks.
          Available In:
        • SonarQube IdeCatch issues on the fly,
          in your IDE
        • SonarQube CloudDetect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories
        • SonarQube ServerAnalyze code in your
          on-premise CI
          Developer Edition
          Available Since
          9.1

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use